New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markers module: PEP8 fixes and MEP10 documentation fixes #1803
Conversation
"^" triangle_up | ||
"<" triangle_left | ||
">" triangle_right | ||
"1" tri_down |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using your syntax I read this as 1
not '1'
. As far as I can see, this makes a big difference (tri_down
vs tickleft
).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have a better way to denote a string? I've used the same syntax as for other strings (">", "^", etc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How are we indicating 'none' as opposed to the python None? I would do the
same as that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So it is consistant with the way it currently is. I'll document everything soon, so that we have a reference document with all the details of the new documentation.
Looks good. Merging. |
Markers module: PEP8 fixes and MEP10 documentation fixes
Here is a patch on PEP8 changes and MEP10 compliance of the markers module.
The markers module did not have it's own documentation page for now, as the plots using markers's style imported the docstrings and concatenated them. As we decided not to do this anymore, the module now needs it's own documentation page. This patch implements this.
Cheers,
N